terraform: restructure terraform directory #69
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
First take on restructuring the terraform directory:
terraform/azarm
- azarm is still used in ghaf github action build pipeline as aarch64 remote builder machine.terraform/main.tf
now describes azure infra configuration based on Florian's PR#35terraform
directory, atterraform/jenkins-controller.tf
,terraform/binary-cache.tf
, andterraform/builder.tf
terraform/modules
terraform/state-storage
describes the shared tfstate storage used to store the terraform state on Azureterraform/persistent
describes the persistent data, not removed when development environments (ghaf-infra instances) are removed. Currently, such persistent data includes binary cache signing key, builder ssh key, and binary cache storage. 'dev' environments share one instance of such persistent data, whereas,prod
environment(s) will have their own set of keys and binary cache storage.init-ghaf-infra.sh
to automate the initial setup of thestate-storage
andpersistent
dataRelevant documentation needs to be re-written, which will be done with a follow-up PR.